Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UISACQCOMP-223: ECS - Add reusable custom hooks to fix invalid reference issues related to holding names and locations #824

Merged
merged 6 commits into from
Oct 29, 2024

Conversation

alisher-epam
Copy link
Contributor

@alisher-epam alisher-epam commented Oct 24, 2024

Purpose

UISACQCOMP-223: ECS - Add reusable custom hooks to fix invalid reference issues related to holding names and locations to support those tickets UIOR-1330 and UIREC-393

Approach

Pre-Merge Checklist

Before merging this PR, please go through the following list and take appropriate actions.

  • I've added appropriate record to the CHANGELOG.md
  • Does this PR meet or exceed the expected quality standards?
    • Code coverage on new code is 80% or greater
    • Duplications on new code is 3% or less
    • There are no major code smells or security issues
  • Does this introduce breaking changes?
    • If any API-related changes - okapi interfaces and permissions are reviewed/changed correspondingly
    • There are no breaking changes in this PR.

If there are breaking changes, please STOP and consider the following:

  • What other modules will these changes impact?
  • Do JIRAs exist to update the impacted modules?
    • If not, please create them
    • Do they contain the appropriate level of detail? Which endpoints/schemas changed, etc.
    • Do they have all they appropriate links to blocked/related issues?
  • Are the JIRAs under active development?
    • If not, contact the project's PO and make sure they're aware of the urgency.
  • Do PRs exist for these changes?
    • If so, have they been approved?

Ideally all of the PRs involved in breaking changes would be merged in the same day to avoid breaking the folio-testing environment. Communication is paramount if that is to be achieved, especially as the number of intermodule and inter-team dependencies increase.

While it's helpful for reviewers to help identify potential problems, ensuring that it's safe to merge is ultimately the responsibility of the PR assignee.

@alisher-epam alisher-epam requested review from usavkov-epam and a team October 24, 2024 15:48
@alisher-epam alisher-epam self-assigned this Oct 24, 2024
Copy link

github-actions bot commented Oct 24, 2024

Jest Unit Test Statistics

    1 files  ±0  217 suites  +3   3m 53s ⏱️ -3s
566 tests +9  564 ✔️ +9  2 💤 ±0  0 ±0 
569 runs  +9  567 ✔️ +9  2 💤 ±0  0 ±0 

Results for commit cae8bfc. ± Comparison against base commit 9285e73.

♻️ This comment has been updated with latest results.

Copy link

github-actions bot commented Oct 24, 2024

BigTest Unit Test Statistics

0 tests  ±0   0 ✔️ ±0   0s ⏱️ ±0s
0 suites ±0   0 💤 ±0 
0 files   ±0   0 ±0 

Results for commit cae8bfc. ± Comparison against base commit 9285e73.

♻️ This comment has been updated with latest results.

@alisher-epam
Copy link
Contributor Author

@usavkov-epam


const DEFAULT_DATA = [];

export const useHoldingsAndLocations = ({
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The hook's name is too general given that it requires many specific arguments.


import { useCurrentUserTenants } from '../consortia';

export const useReceivingTenantIdsAndLocations = ({
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you please leave the purpose of this hook in the comments?


const DEFAULT_DATA = [];

export const getHoldingLocations = async ({
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Based on the name of this function, I expect to get a list of locations for a specific holding according to certain parameters, not for a list of holdings.

};
};

export const getHoldingLocationsByTenants = async ({
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

similar here

Copy link

@alisher-epam
Copy link
Contributor Author

@folio-org/fe-tl-reviewers ^^^ please review

@alisher-epam alisher-epam merged commit 330bcac into master Oct 29, 2024
6 checks passed
@alisher-epam alisher-epam deleted the UISACQCOMP-223 branch October 29, 2024 13:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants